Application of uplink transmission configuration indicator state with downlink reference signal to codebook based transmissions

ABSTRACT

Certain aspects of the present disclosure provide techniques for applying uplink transmission configuration indicator (TCI) states with downlink reference signals to codebook based physical uplink shared channel (PUSCH) transmissions. An example method generally includes receiving, from a network entity, signaling of an uplink transmission configuration indicator (TCI) state with a target codebook based uplink transmission signal, determining if the TCI state has a source downlink reference signal (RS) and deciding how to process the codebook based uplink transmission based on the determination.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims benefit of and priority to U.S. ProvisionalApplication No. 62/951,729, filed Dec. 20, 2019, which is herebyassigned to the assignee hereof and hereby expressly incorporated byreference herein in its entirety as if fully set forth below and for allapplicable purposes.

BACKGROUND Field of the Disclosure

Aspects of the present disclosure relate to wireless communications, andmore particularly, to techniques for applying uplink transmissionconfiguration indicator (TCI) states with downlink reference signals tocodebook based physical uplink shared channel (PUSCH) transmissions.

Description of Related Art

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,broadcasts, etc. These wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, etc.). Examples of such multiple-access systems include3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)systems, LTE Advanced (LTE-A) systems, code division multiple access(CDMA) systems, time division multiple access (TDMA) systems, frequencydivision multiple access (FDMA) systems, orthogonal frequency divisionmultiple access (OFDMA) systems, single-carrier frequency divisionmultiple access (SC-FDMA) systems, and time division synchronous codedivision multiple access (TD-SCDMA) systems, to name a few.

These multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent wireless devices to communicate on a municipal, national,regional, and even global level. New radio (e.g., 5G NR) is an exampleof an emerging telecommunication standard. NR is a set of enhancementsto the LTE mobile standard promulgated by 3GPP. NR is designed to bettersupport mobile broadband Internet access by improving spectralefficiency, lowering costs, improving services, making use of newspectrum, and better integrating with other open standards using OFDMAwith a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL).To these ends, NR supports beamforming, multiple-input multiple-output(MIMO) antenna technology, and carrier aggregation.

However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in NR and LTEtechnology. Preferably, these improvements should be applicable to othermulti-access technologies and the telecommunication standards thatemploy these technologies.

BRIEF SUMMARY

The systems, methods, and devices of the disclosure each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure as expressedby the claims which follow, some features will now be discussed briefly.After considering this discussion, and particularly after reading thesection entitled “Detailed Description” one will understand how thefeatures of this disclosure provide advantages that include improvedcommunications between access points and stations in a wireless network.

Certain aspects of the subject matter described in this disclosure canbe implemented in a method for wireless communication performed by auser equipment (UE). The method generally includes receiving, from anetwork entity, signaling of an uplink transmission configurationindicator (TCI) state for a target codebook based uplink transmissionsignal. The method generally includes determining if the TCI state has asource downlink reference signal (RS). The method generally includesdeciding how to process the codebook based uplink transmission based onthe determination.

Certain aspects of the present disclosure provide a method for wirelesscommunication by a network entity. The method generally includessending, to a UE, signaling of an uplink TCI state for a target codebookbased uplink transmission signal. The method generally includesdetermining how the UE processed the codebook based uplink transmission,based on whether the TCI state has a source downlink RS. The methodgenerally includes processing the codebook based uplink transmission inaccordance with the determination.

Certain aspects of the subject matter described in this disclosure canbe implemented in an apparatus for wireless communication. The apparatusgenerally includes at least one processor; and memory coupled to the atleast one processor. The memory generally includes code executable bythe at least one processor to cause the apparatus to receive, from anetwork entity, signaling of an uplink TCI state for a target codebookbased uplink transmission signal. The memory generally includes codeexecutable by the at least one processor to cause the apparatus todetermine if the TCI state has a source downlink RS. The memorygenerally includes code executable by the at least one processor tocause the apparatus to decide how to process the codebook based uplinktransmission based on the determination.

Certain aspects of the subject matter described in this disclosure canbe implemented in an apparatus for wireless communication. The apparatusgenerally includes at least one processor; and memory coupled to the atleast one processor. The memory generally includes code executable bythe at least one processor to cause the apparatus to send, to a UE,signaling of an uplink TCI state for a target codebook based uplinktransmission signal. The memory generally includes code executable bythe at least one processor to cause the apparatus to determine how theUE processed the codebook based uplink transmission, based on whetherthe TCI state has a source downlink RS. The memory generally includescode executable by the at least one processor to cause the apparatus toprocess the codebook based uplink transmission in accordance with thedetermination.

Certain aspects of the subject matter described in this disclosure canbe implemented in an apparatus for wireless communication. The apparatusgenerally includes means for receiving, from a network entity, signalingof an uplink transmission configuration indicator (TCI) state for atarget codebook based uplink transmission signal. The apparatusgenerally includes means for determining if the TCI state has a sourcedownlink RS. The apparatus generally includes means for deciding how toprocess the codebook based uplink transmission based on thedetermination.

Certain aspects of the present disclosure provide an apparatus forwireless communication. The apparatus generally includes means for send,to a UE, signaling of an uplink TCI state for a target codebook baseduplink transmission signal. The apparatus generally includes means fordetermining how the UE processed the codebook based uplink transmission,based on whether the TCI state has a source downlink RS. The apparatusgenerally includes means for processing the codebook based uplinktransmission in accordance with the determination.

Certain aspects of the subject matter described in this disclosure canbe implemented in a computer readable medium storing computer executablecode thereon for wireless communication. The computer readable mediumgenerally includes code for receiving, from a network entity, signalingof an uplink TCI state for a target codebook based uplink transmissionsignal. The computer readable medium generally includes code fordetermining if the TCI state has a source downlink RS. The computerreadable medium generally includes code for deciding how to process thecodebook based uplink transmission based on the determination.

Certain aspects of the present disclosure provide a computer readablemedium storing computer executable code thereon for wirelesscommunication. The computer readable medium generally includes code forsending, to a UE, signaling of an uplink TCI state for a target codebookbased uplink transmission signal. The computer readable medium generallyincludes code for determining how the UE processed the codebook baseduplink transmission, based on whether the TCI state has a sourcedownlink RS. The computer readable medium generally includes code forprocessing the codebook based uplink transmission in accordance with thedetermination.

To the accomplishment of the foregoing and related ends, the one or moreaspects comprise the features hereinafter fully described andparticularly pointed out in the claims. The following description andthe appended drawings set forth in detail certain illustrative featuresof the one or more aspects. These features are indicative, however, ofbut a few of the various ways in which the principles of various aspectsmay be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above-recited features of the presentdisclosure can be understood in detail, a more particular description,briefly summarized above, may be had by reference to aspects, some ofwhich are illustrated in the drawings. It is to be noted, however, thatthe appended drawings illustrate only certain typical aspects of thisdisclosure and are therefore not to be considered limiting of its scope,for the description may admit to other equally effective aspects.

FIG. 1 is a block diagram conceptually illustrating an exampletelecommunications system, in accordance with certain aspects of thepresent disclosure.

FIG. 2 is a block diagram illustrating an example logical architectureof a distributed radio access network (RAN), in accordance with certainaspects of the present disclosure.

FIG. 3 is a diagram illustrating an example physical architecture of adistributed RAN, in accordance with certain aspects of the presentdisclosure.

FIG. 4 is a block diagram conceptually illustrating a design of anexample base station (BS) and user equipment (UE), in accordance withcertain aspects of the present disclosure.

FIG. 5 is a diagram showing examples for implementing a communicationprotocol stack, in accordance with certain aspects of the presentdisclosure.

FIG. 6 illustrates an example of a frame format for a new radio (NR)system, in accordance with certain aspects of the present disclosure.

FIG. 7 illustrates how different synchronization signal blocks (SSBs)may be sent using different beams, in accordance with certain aspects ofthe present disclosure.

FIG. 8 shows an exemplary transmission resource mapping, according toaspects of the present disclosure.

FIG. 9 illustrates example quasi co-location (QCL) relationships, inaccordance with certain aspects of the present disclosure.

FIG. 10 is a call flow diagram illustrating an example of codebook basedUL transmission.

FIG. 11 is a flow diagram illustrating example operations for wirelesscommunications by a user equipment (UE), in accordance with certainaspects of the present disclosure.

FIG. 12 is a flow diagram illustrating example operations for wirelesscommunications by a network entity, in accordance with certain aspectsof the present disclosure.

FIG. 13 is a call flow diagram illustrating an example of codebook basedUL transmission with uplink TCI states.

FIG. 14 is a call flow diagram illustrating an example of codebook basedUL transmission with uplink TCI states.

FIG. 15 illustrates a communications device that may include variouscomponents configured to perform operations for the techniques disclosedherein in accordance with aspects of the present disclosure.

FIG. 16 illustrates a communications device that may include variouscomponents configured to perform operations for the techniques disclosedherein in accordance with aspects of the present disclosure.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures. It is contemplated that elements disclosed in one aspectmay be beneficially utilized on other aspects without specificrecitation.

DETAILED DESCRIPTION

Aspects of the present disclosure provide apparatus, methods, processingsystems, and computer readable mediums for applying uplink transmissionconfiguration indicator (TCI) states with downlink reference signals tocodebook based physical uplink shared channel (PUSCH) transmissions.

The following description provides examples of applying uplink TCIstates with downlink references signals to codebook based transmissionsin communication systems, and is not limiting of the scope,applicability, or examples set forth in the claims. Changes may be madein the function and arrangement of elements discussed without departingfrom the scope of the disclosure. Various examples may omit, substitute,or add various procedures or components as appropriate. For instance,the methods described may be performed in an order different from thatdescribed, and various steps may be added, omitted, or combined. Also,features described with respect to some examples may be combined in someother examples. For example, an apparatus may be implemented or a methodmay be practiced using any number of the aspects set forth herein. Inaddition, the scope of the disclosure is intended to cover such anapparatus or method which is practiced using other structure,functionality, or structure and functionality in addition to, or otherthan, the various aspects of the disclosure set forth herein. It shouldbe understood that any aspect of the disclosure disclosed herein may beembodied by one or more elements of a claim. The word “exemplary” isused herein to mean “serving as an example, instance, or illustration.”Any aspect described herein as “exemplary” is not necessarily to beconstrued as preferred or advantageous over other aspects.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular radioaccess technology (RAT) and may operate on one or more frequencies. ARAT may also be referred to as a radio technology, an air interface,etc. A frequency may also be referred to as a carrier, a subcarrier, afrequency channel, a tone, a subband, etc. Each frequency may support asingle RAT in a given geographic area in order to avoid interferencebetween wireless networks of different RATs.

The techniques described herein may be used for various wirelessnetworks and radio technologies. While aspects may be described hereinusing terminology commonly associated with 3G, 4G, and/or new radio(e.g., 5G NR) wireless technologies, aspects of the present disclosurecan be applied in other generation-based communication systems.

NR access may support various wireless communication services, such asenhanced mobile broadband (eMBB) targeting wide bandwidth, millimeterwave mmW, massive machine type communications MTC (mMTC) targetingnon-backward compatible MTC techniques, and/or mission criticaltargeting ultra-reliable low-latency communications (URLLC). Theseservices may include latency and reliability requirements. Theseservices may also have different transmission time intervals (TTI) tomeet respective quality of service (QoS) requirements. In addition,these services may co-exist in the same subframe.

NR supports beamforming and beam direction may be dynamicallyconfigured. MIMO transmissions with precoding may also be supported.MIMO configurations in the DL may support up to 8 transmit antennas withmulti-layer DL transmissions up to 8 streams and up to 2 streams per UE.Multi-layer transmissions with up to 2 streams per UE may be supported.Aggregation of multiple cells may be supported with up to 8 servingcells.

FIG. 1 illustrates an example wireless communication network 100 (e.g.,an NR/5G network), in which aspects of the present disclosure may beperformed. For example, the wireless communication network 100 mayinclude BSs 110 and UEs 120 configured to uplink TCI states withdownlink references signals to codebook based transmissions. As shown inFIG. 1 , the BS 110 a includes a TCI state manager 112 that processesthe codebook based uplink transmission in accordance with how the UEprocessed the codebook based uplink transmission, in accordance withaspects of the present disclosure. The UE 120 a includes a TCI statemanager 122 that decides how to process a codebook based uplinktransmission based on if a TCI state has a source downlink referencesignal (RS), in accordance with aspects of the present disclosure.

The wireless communication network 100 may be an NR system (e.g., a 5GNR network). As shown in 1, the wireless communication network 100 maybe in communication with a core network 132. The core network 132 may incommunication with one or more base station (BSs) 110 a-z (each alsoindividually referred to herein as BS 110 or collectively as BSs 110)and/or user equipment (UE) 120 a-y (each also individually referred toherein as UE 120 or collectively as UEs 120) in the wirelesscommunication network 100 via one or more interfaces.

A BS may provide communication coverage for a particular geographicarea, sometimes referred to as a “cell”, which may be stationary or maymove according to the location of a mobile BS 110. In some examples, thebase stations may be interconnected to one another and/or to one or moreother base stations or network nodes (not shown) in wirelesscommunication network 100 through various types of backhaul interfaces,such as a direct physical connection, a wireless connection, a virtualnetwork, or the like using any suitable transport network.

In the example shown in FIG. 1 , the BSs 110 a, 110 b and 110 c may bemacro BSs for the macro cells 102 a, 102 b and 102 c, respectively. TheBS 110 x may be a pico BS for a pico cell 102 x. The BSs 110 y and 110 zmay be femto BSs for the femto cells 102 y and 102 z, respectively. A BSmay support one or multiple cells.

The BSs 110 communicate with UEs 120 in the wireless communicationnetwork 100. The UEs 120 (e.g., 120 x, 120 y, etc.) may be dispersedthroughout the wireless network 100, and each UE may be stationary ormobile. Wireless communication network 100 may also include relaystations (e.g., relation station 110 r), also referred to as relays orthe like, that receive a transmission of data and/or other informationfrom an upstream station (e.g., a BS 110 a or a UE 120 r) and sends atransmission of the data and/or other information to a downstreamstation (e.g., a UE 120 or a BS 110), or that relays transmissionsbetween UEs 120 to facilitate communication between devices.

A network controller 130 may couple to a set of BSs and providecoordination and control for these BSs (e.g., via a backhaul). Inaspects, the network controller 130 may be in communication with a corenetwork 132 (e.g., a 5G Core Network (5GC)), which provides variousnetwork functions such as Access and Mobility Management, SessionManagement, User Plane Function, Policy Control Function, AuthenticationServer Function, Unified Data Management, Application Function, NetworkExposure Function, Network Repository Function, Network Slice SelectionFunction, etc.

FIG. 2 illustrates an example logical architecture of a distributedRadio Access Network (RAN) 200, which may be implemented in the wirelesscommunication network 100 illustrated in FIG. 1 . A 5G access node 206may include an access node controller (ANC) 202. ANC 202 may be acentral unit (CU) of the distributed RAN 200. The backhaul interface tothe Next Generation Core Network (NG-CN) 204 may terminate at ANC 202.The backhaul interface to neighboring next generation access Nodes(NG-ANs) 210 may terminate at ANC 202. ANC 202 may include one or moretransmission reception points (TRPs) 208 (e.g., cells, BSs, gNBs, etc.).

The TRPs 208 may be a distributed unit (DU). TRPs 208 may be connectedto a single ANC (e.g., ANC 202) or more than one ANC (not illustrated).For example, for RAN sharing, radio as a service (RaaS), and servicespecific ANC deployments, TRPs 208 may be connected to more than oneANC. TRPs 208 may each include one or more antenna ports. TRPs 208 maybe configured to individually (e.g., dynamic selection) or jointly(e.g., joint transmission) serve traffic to a UE.

The logical architecture of distributed RAN 200 may support variousbackhauling and fronthauling solutions. This support may occur via andacross different deployment types. For example, the logical architecturemay be based on transmit network capabilities (e.g., bandwidth, latency,and/or jitter).

The logical architecture of distributed RAN 200 may share featuresand/or components with LTE. For example, next generation access node(NG-AN) 210 may support dual connectivity with NR and may share a commonfronthaul for LTE and NR.

The logical architecture of distributed RAN 200 may enable cooperationbetween and among TRPs 208, for example, within a TRP and/or across TRPsvia ANC 202. An inter-TRP interface may not be used.

Logical functions may be dynamically distributed in the logicalarchitecture of distributed RAN 200. As will be described in more detailwith reference to FIG. 5 , the Radio Resource Control (RRC) layer,Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC)layer, Medium Access Control (MAC) layer, and a Physical (PHY) layersmay be adaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

FIG. 3 illustrates an example physical architecture of a distributedRadio Access Network (RAN) 300, according to aspects of the presentdisclosure. A centralized core network unit (C-CU) 302 may host corenetwork functions. C-CU 302 may be centrally deployed. C-CU 302functionality may be offloaded (e.g., to advanced wireless services(AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions.Optionally, the C-RU 304 may host core network functions locally. TheC-RU 304 may have distributed deployment. The C-RU 304 may be close tothe network edge.

A DU 306 may host one or more TRPs (Edge Node (EN), an Edge Unit (EU), aRadio Head (RH), a Smart Radio Head (SRH), or the like). The DU may belocated at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of BS 110 and UE 120 (as depictedin FIG. 1 ), which may be used to implement aspects of the presentdisclosure.

At the BS 110, a transmit processor 420 may receive data from a datasource 412 and control information from a controller/processor 440. Thecontrol information may be for the physical broadcast channel (PBCH),physical control format indicator channel (PCFICH), physical hybrid ARQindicator channel (PHICH), physical downlink control channel (PDCCH),group common PDCCH (GC PDCCH), etc. The data may be for the physicaldownlink shared channel (PDSCH), etc. The processor 420 may process(e.g., encode and symbol map) the data and control information to obtaindata symbols and control symbols, respectively. The processor 420 mayalso generate reference symbols, e.g., for the primary synchronizationsignal (PSS), secondary synchronization signal (SSS), and cell-specificreference signal (CRS). A transmit (TX) multiple-input multiple-output(MIMO) processor 430 may perform spatial processing (e.g., precoding) onthe data symbols, the control symbols, and/or the reference symbols, ifapplicable, and may provide output symbol streams to the modulators(MODs) in transceivers 432 a through 432 t. Each modulator may process arespective output symbol stream (e.g., for OFDM, etc.) to obtain anoutput sample stream. Each modulator may further process (e.g., convertto analog, amplify, filter, and upconvert) the output sample stream toobtain a downlink signal. Downlink signals from the modulators intransceivers 432 a through 432 t may be transmitted via the antennas 434a through 434 t, respectively.

At the UE 120, antennas 452 a through 452 r may receive downlink signalsfrom the base station 110 and may provide received signals todemodulators (DEMODs) in transceivers in transceivers 454 a through 454r, respectively. Each demodulator may condition (e.g., filter, amplify,down convert, and digitize) a respective received signal to obtain inputsamples. Each demodulator may further process input samples (e.g., forOFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtainreceived symbols from all demodulators in transceivers 454 a through 454r, perform MIMO detection on the received symbols if applicable, andprovide detected symbols. A receive processor 458 may process (e.g.,demodulate, deinterleave, and decode) the detected symbols, providedecoded data for the UE 120 to a data sink 460, and provide decodedcontrol information to a controller/processor 480.

On the uplink, at UE 120, a transmit processor 464 may receive andprocess data (e.g., for the physical uplink shared channel (PUSCH)) froma data source 462 and control information (e.g., for the physical uplinkcontrol channel (PUCCH) from the controller/processor 480. The transmitprocessor 464 may also generate reference symbols for a reference signal(e.g., for the sounding reference signal (SRS)). The symbols from thetransmit processor 464 may be precoded by a TX MIMO processor 466 ifapplicable, further processed by the demodulators in transceivers 454 athrough 454 r (e.g., for SC-FDM, etc.), and transmitted to the basestation 110. At the BS 110, uplink signals from the UE 120 may bereceived by the antennas 434, processed by the modulators 432, detectedby a MIMO detector 436 if applicable, and further processed by a receiveprocessor 438 to obtain decoded data and control information sent by theUE 120. The receive processor 438 may provide the decoded data to a datasink 439 and the decoded control information to the controller/processor440.

The memories 442 and 482 may store data and program codes for BS 110 andUE 120, respectively. A scheduler 444 may schedule UEs for datatransmission on the downlink and/or uplink.

Antennas 252, processors 266, 258, 264, and/or controller/processor 280of the UE 120 and/or antennas 234, processors 220, 230, 238, and/orcontroller/processor 240 of the BS 110 may be used to perform thevarious techniques and methods described herein. For example, as shownin FIG. 4 , the controller/processor 240 of the BS 110 a has a TCI statemanager 241 that processes a codebook based uplink transmission inaccordance with how the UE processed the codebook based uplinktransmission, according to aspects described herein. As shown in FIG. 4, the controller/processor 280 of the UE 120 a has a TCI state manager281 that decides how to process a codebook based uplink transmissionbased on if a TCI state has a source downlink reference signal (RS),according to aspects described herein. Although shown at thecontroller/processor, other components of the UE 120 a and BS 110 a maybe used to perform the operations described herein.

FIG. 5 illustrates a diagram 500 showing examples for implementing acommunications protocol stack, according to aspects of the presentdisclosure. The illustrated communications protocol stacks may beimplemented by devices operating in a wireless communication system,such as a 5G system (e.g., a system that supports uplink-basedmobility). Diagram 500 illustrates a communications protocol stackincluding a Radio Resource Control (RRC) layer 510, a Packet DataConvergence Protocol (PDCP) layer 515, a Radio Link Control (RLC) layer520, a Medium Access Control (MAC) layer 525, and a Physical (PHY) layer530. In various examples, the layers of a protocol stack may beimplemented as separate modules of software, portions of a processor orASIC, portions of non-collocated devices connected by a communicationslink, or various combinations thereof. Collocated and non-collocatedimplementations may be used, for example, in a protocol stack for anetwork access device (e.g., ANs, CUs, and/or DUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack,in which implementation of the protocol stack is split between acentralized network access device (e.g., an ANC 202 in FIG. 2 ) anddistributed network access device (e.g., DU 208 in FIG. 2 ). In thefirst option 505-a, an RRC layer 510 and a PDCP layer 515 may beimplemented by the central unit, and an RLC layer 520, a MAC layer 525,and a PHY layer 530 may be implemented by the DU. In various examplesthe CU and the DU may be collocated or non-collocated. The first option505-a may be useful in a macro cell, micro cell, or pico celldeployment.

A second option 505-b shows a unified implementation of a protocolstack, in which the protocol stack is implemented in a single networkaccess device. In the second option, RRC layer 510, PDCP layer 515, RLClayer 520, MAC layer 525, and PHY layer 530 may each be implemented bythe AN. The second option 505-b may be useful in, for example, a femtocell deployment.

Regardless of whether a network access device implements part or all ofa protocol stack, a UE may implement an entire protocol stack as shownin 505-c (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer520, the MAC layer 525, and the PHY layer 530).

NR may utilize orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) on the uplink and downlink. NR may supporthalf-duplex operation using time division duplexing (TDD). OFDM andsingle-carrier frequency division multiplexing (SC-FDM) partition thesystem bandwidth into multiple orthogonal subcarriers, which are alsocommonly referred to as tones, bins, etc. Each subcarrier may bemodulated with data. Modulation symbols may be sent in the frequencydomain with OFDM and in the time domain with SC-FDM. The spacing betweenadjacent subcarriers may be fixed, and the total number of subcarriersmay be dependent on the system bandwidth. The minimum resourceallocation, called a resource block (RB), may be 12 consecutivesubcarriers. The system bandwidth may also be partitioned into subbands.For example, a subband may cover multiple RBs. NR may support a basesubcarrier spacing (SCS) of 15 KHz and other SCS may be defined withrespect to the base SCS (e.g., 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc.).

FIG. 6 is a diagram showing an example of a frame format 600 for NR. Thetransmission timeline for each of the downlink and uplink may bepartitioned into units of radio frames. Each radio frame may have apredetermined duration (e.g., 10 ms) and may be partitioned into 10subframes, each of 1 ms, with indices of 0 through 9. Each subframe mayinclude a variable number of slots (e.g., 1, 2, 4, 8, 16, . . . slots)depending on the SCS. Each slot may include a variable number of symbolperiods (e.g., 7, 12, or 14 symbols) depending on the SCS. The symbolperiods in each slot may be assigned indices. A sub-slot structure mayrefer to a transmit time interval having a duration less than a slot(e.g., 2, 3, or 4 symbols). Each symbol in a slot may be configured fora link direction (e.g., DL, UL, or flexible) for data transmission andthe link direction for each subframe may be dynamically switched. Thelink directions may be based on the slot format. Each slot may includeDL/UL data as well as DL/UL control information.

In NR, a synchronization signal block (SSB) is transmitted. In certainaspects, SSBs may be transmitted in a burst where each SSB in the burstcorresponds to a different beam direction for UE-side beam management(e.g., including beam selection and/or beam refinement). The SSBincludes a PSS, a SSS, and a two symbol PBCH. The SSB can be transmittedin a fixed slot location, such as the symbols 0-3 as shown in FIG. 3 .The PSS and SSS may be used by UEs for cell search and acquisition. ThePSS may provide half-frame timing, the SS may provide the CP length andframe timing. The PSS and SSS may provide the cell identity. The PBCHcarries some basic system information, such as downlink systembandwidth, timing information within radio frame, SS burst setperiodicity, system frame number, etc. The SSBs may be organized into SSbursts to support beam sweeping. Further system information such as,remaining minimum system information (RMSI), system information blocks(SIBs), other system information (OSI) can be transmitted on a physicaldownlink shared channel (PDSCH) in certain subframes. The SSB can betransmitted up to sixty-four times, for example, with up to sixty-fourdifferent beam directions for mmWave. The multiple transmissions of theSSB are referred to as a SS burst set. SSBs in an SS burst set may betransmitted in the same frequency region, while SSBs in different SSbursts sets can be transmitted at different frequency regions.

As shown in FIG. 7 , the SS blocks may be organized into SS burst setsto support beam sweeping. As shown, each SSB within a burst set may betransmitted using a different beam, which may help a UE quickly acquireboth transmit (Tx) and receive (Rx) beams (particular for mmWapplications). A physical cell identity (PCI) may still decoded from thePSS and SSS of the SSB.

Certain deployment scenarios may include one or both NR deploymentoptions. Some may be configured for non-standalone (NSA) and/orstandalone (SA) option. A standalone cell may need to broadcast both SSBand remaining minimum system information (RMSI), for example, with SIB1and SIB2. A non-standalone cell may only need to broadcast SSB, withoutbroadcasting RMSI. In a single carrier in NR, multiple SSBs may be sentin different frequencies, and may include the different types of SSB.

Operating characteristics of a gNB in an NR communications system may bedependent on a frequency range (FR) in which the system operates. Afrequency range may include one or more operating bands (e.g., “n1”band, “n2” band, “n7” band, and “n41” band, etc.). A communicationssystem (e.g., one or more gNBs and UEs) may operate in one or moreoperating bands.

A control resource set (CORESET) for an orthogonal frequency divisionmultiple access (OFDMA) system (e.g., a communications systemtransmitting physical downlink control channel (PDCCH) using OFDMAwaveforms) may include one or more control resource (e.g., time andfrequency resources) sets, configured for conveying PDCCH, within thesystem bandwidth. Within each CORESET, one or more search spaces (e.g.,common search space (CSS), UE-specific search space (USS), etc.) may bedefined for a given UE. Search spaces are generally areas or portionswhere a communication device (e.g., a UE) may look for (e.g., monitor)control information.

A CORESET may be defined in units of resource element groups (REGs).Each REG may include a fixed number (e.g., twelve) of tones in onesymbol period (e.g., a symbol period of a slot), where one tone in onesymbol period is referred to as a resource element (RE). A fixed numberof REGs may be included in a control channel element (CCE). Sets of CCEsmay be used to transmit new radio PDCCHs (NR-PDCCHs), with differentnumbers of CCEs in the sets used to transmit NR-PDCCHs using differingaggregation levels. Multiple sets of CCEs may be defined as searchspaces for UEs. A gNB may transmit a NR-PDCCH to a UE in a set of CCEs,called a decoding candidate, within a search space for the UE. The UEmay receive the NR-PDCCH by searching (e.g., monitoring) in searchspaces and decoding the NR-PDCCH.

During initial access, a UE may identify an initial CORESET (e.g.,referred to as CORESET #0) configuration from an indication (e.g., apdcchConfigSIB1) in a system information (e.g., in a maser informationblock (MIB) carried in PBCH). This initial CORESET may then be used toconfigure the UE (e.g., with other CORESETs and/or bandwidth parts viadedicated (UE-specific) signaling). When the UE detects a controlchannel in the CORESET, the UE attempts to decode the control channeland the UE communicates with the transmitting BS (e.g., the transmittingcell) according to the control information provided in a decoded controlchannel.

When a UE is connected to a cell (or BS), the UE may receive a masterinformation block (MIB). The MIB can be in a synchronization signal andphysical broadcast channel (SS/PBCH) block (e.g., in the PBCH of theSS/PBCH block) on a synchronization raster (sync raster). In somescenarios, the sync raster may correspond to a synchronization signalblock (SSB). From the frequency of the sync raster, the UE may determinean operating band of the cell. Based on a cell's operation band, the UEmay determine a minimum channel bandwidth and a subcarrier spacing (SCS)of the channel. The UE may then determine an index from the MIB (e.g.,four bits in the MIB, conveying an index in a range 0-15).

Given this index, the UE may look up or locate a CORESET configuration(this initial CORESET configured via the MIB is generally referred to asthe CORESET #0). This may be accomplished from one or more tables ofCORESET configurations. These configurations (including single tablescenarios) may include various subsets of indices indicating validCORESET configurations for various combinations of minimum channelbandwidth and SCS. In some arrangements, each combination of minimumchannel bandwidth and SCS may be mapped to a subset of indices in thetable.

Alternatively or additionally, the UE may select a search space CORESETconfiguration table from several tables of CORESET configurations. Theseconfigurations can be based on a minimum channel bandwidth and SCS. TheUE may then look up a CORESET configuration (e.g., a Type0-PDCCH searchspace CORESET configuration) from the selected table, based on theindex. After determining the CORESET configuration (e.g., from thesingle table or the selected table), the UE may then determine theCORESET to be monitored (as mentioned above) based on the location (intime and frequency) of the SS/PBCH block and the CORESET configuration.

FIG. 8 shows an example transmission resource mapping 800, according toaspects of the present disclosure. In the exemplary mapping, a BS (e.g.,BS 110 a, shown in FIG. 1 ) transmits an SS/PBCH block 802. The SS/PBCHblock includes a MIB conveying an index to a table that relates the timeand frequency resources of the CORESET 804 to the time and frequencyresources of the SS/PBCH block.

The BS may also transmit control signaling. In some scenarios, the BStransmits the control signaling in a PDCCH to a UE (e.g., UE 120, shownin FIG. 1 ) in the (time/frequency resources of the) CORESET 804. ThePDCCH may schedule a PDSCH 806. The BS then transmits the PDSCH 806 tothe UE. The UE may receive the MIB in the SS/PBCH block 802, determinethe index, look up a CORESET configuration based on the index, anddetermine the CORESET 804 from the CORESET configuration and the SS/PBCHblock. The UE may then monitor the CORESET 804, decode the PDCCH in theCORESET 804, and receive the PDSCH 806 that was allocated by the PDCCH.

Different CORESET configurations may have different parameters thatdefine a corresponding CORESET. For example, each configuration mayindicate a number of resource blocks (e.g., 24, 48, or 96), a number ofsymbols (e.g., 1-3), as well as an offset (e.g., 0-38 RBs) thatindicates a location in frequency.

As discussed above, aspects of the disclosure relate to uplink transmitbeam states using transmission configuration indication (TCI).

It is desirable for a user equipment (UE) to know which assumptions theUE can make on a channel for different transmissions. For example, theUE may need to know which reference signals it can use to estimate thechannel in order to decode a transmitted signal (e.g., physical downlinkcontrol channel (PDCCH) or physical downlink shared channel (PDSCH)). Itmay also be important for the UE to be able to report relevant channelstate information (CSI) to the base station (BS) (e.g., next generationNodeB (gNB)) for scheduling, link adaptation, and/or beam managementpurposes. In new radio (NR), the concept of quasi co-location (QCL) andstates is used to convey information about these assumptions.

QCL assumptions are generally defined in terms of channel properties.3GPP TS 38.214 defines QCL as “two antenna ports are said to bequasi-co-located if properties of the channel over which a symbol on oneantenna port is conveyed can be inferred from the channel over which asymbol on the other antenna port is conveyed.” Different referencesignals (RSs) may be considered quasi co-located (QCL'd) if a receiver(e.g., a UE) can apply channel properties determined by detecting afirst reference signal to help detect a second signal. TCI statesgenerally include configurations such as QCL-relationships, for example,between the downlink (DL) RSs in one channel state information referencesignal (CSI-RS) set and the PDSCH demodulation reference signal (DMRS)ports.

In some cases, a UE may be configured with up to M TCI States.Configuration of the M TCI States may be via higher layer signalling(e.g., a higher layer parameter TCI-States). A UE may be signalled todecode PDSCH according to a detected PDCCH with downlink controlinformation (DCI) indicating one of the TCI states. Each configured TCIstate may include one RS set (e.g., by higher layer parameterTCI-RS-SetConfig) that indicates different QCL assumptions betweencertain source and target signals.

QCL signaling may be provided for RSs and channels across scenariosinvolving multiple cells, such as in coordinated multipoint (CoMP)scenarios in which multiple transmit receive points (TRPs) or integratedaccess and backhaul (IAB) nodes each have their own cell ID.

FIG. 9 is a table 900 illustrating examples of the association of DLreference signals with corresponding QCL types that may be indicated bya parameter (e.g., TCI-RS-SetConfig).

The table 900 shows source RSs, target RSs, and QCL type assumptionsthat may be configured by a valid UL-TCI state configuration. The targetsignal generally refers to a signal for which channel properties may beinferred by measuring those channel properties for an associated sourcesignal. As noted above, a UE may use the source RS to determine variouschannel parameters, depending on the associated QCL type, and use thosevarious channel properties (determined based on the source RS) toprocess the target signal. Examples of source RSs include phase trackingreference signals (PTRSs), SSBs, sounding reference signal (SRS), and/orCSI-RSs (e.g., CSI-RS for beam management). Examples of target RSsinclude aperiodic tracking reference signals (TRSs), periodic TRSs,PRACHs, PUCCHs, and/or PUSCHs. The QCL types include the QCL typesA/B/C/D discussed below.

For the case of two source RSs, the different QCL types can beconfigured for the same target RS. In the illustrative example, asynchronization signal block (SSB) is associated with Type C QCL forperiodic TRS (P-TRS), while CSI-RS for beam management (CSI-RS-BM) isassociated with Type D QCL.

QCL types indicated to the UE can be based on a higher layer parameter(e.g., QCL-Type). QCL types may take one or a combination of thefollowing types:

QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread},

QCL-TypeB: {Doppler shift, Doppler spread},

QCL-TypeC: {average delay, Doppler shift}, and

QCL-TypeD: {Spatial Rx parameter},

Spatial QCL assumptions (QCL-TypeD) may be used to help a UE to selectan analog receive (Rx) beam (e.g., during beam management procedures).For example, an SSB resource indicator may indicate a same beam for aprevious reference signal should be used for a subsequent transmission.

An information element (e.g., CORESET IE) sent via RRC signaling mayconvey information regarding a CORESET configured for a UE. The CORESETIE generally includes a CORESET ID, an indication of frequency domainresources (e.g., number of RBs) assigned to the CORESET, contiguous timeduration of the CORESET in a number of symbols, and TransmissionConfiguration Indicator (TCI) states.

As noted above, a subset of the TCI states provide QCL relationshipsbetween DL RS(s) in one RS set (e.g., a TCI-Set) and another signal(e.g., DMRS ports for another transmission). A particular TCI state fora given UE (e.g., for unicast PDCCH) may be conveyed to the UE by aMAC-CE. The TCI state may be selected from the set of TCI statesconveyed by the CORESET IE, with the initial CORESET (CORESET #0)generally configured via MIB.

Search space information may also be provided via RRC signaling. Forexample, the SearchSpace IE is another RRC IE that defines how and whereto search for PDCCH candidates for a given CORESET. Each search space isassociated with one CORESET. The SearchSpace IE identifies a searchspace configured for a CORESET by a search space ID. In an aspect, thesearch space ID associated with CORESET #0 is SearchSpace ID #0. Thesearch space is generally configured via PBCH (e.g., carried in theMIB).

Some deployments (e.g., NR Release 15 and 16 systems) supportcodebook-based transmission for UL transmissions. Codebook-based ULtransmission may be based on BS feedback.

FIG. 10 is a call flow diagram illustrating an example of conventionalcodebook based UL transmission using a wideband precoder. Asillustrated, a UE transmits (non-precoded) SRS with up to 2 SRSresources (with each resource having 1, 2 or 4 ports). The BS measuresthe SRS and, based on the measurement, selects one SRS resource and awideband precoder to be applied to the SRS ports within the selectedresource.

As illustrated, the BS configures the UE with the selected SRS resourcevia an SRS resource indictor (SRI) and with the wideband precoder via atransmit precoder matrix indicator (TPMI). For a dynamic grant, the SRIand TPMI may be configured via DCI format 0_1. For a configured grant(e.g., for semi-persistent uplink), SRI and TPMI may be configured viaRRC or DCI.

The UE determines the selected SRS resource from the SRI and precodingfrom TPMI and transmits PUSCH accordingly.

Aspects of the present disclosure relate to techniques for applyinguplink TCI states with downlink reference signals to codebook basedphysical uplink transmissions Example Uplink TCI with Downlink RS toCodebook Based PUSCH Transmissions

Aspects of the present disclosure may help apply uplink (UL)transmission configuration indicator (TCI) states to codebook basedphysical uplink shared channel (PUSCH) transmissions, such as thosedescribed above.

As mentioned above, uplink TCI states may provide a mechanism toindicate what parameters to use to (transmit and) decode uplink traffic.The uplink TCI state may have downlink source reference signals (RS) toindicate a beam for uplink PUSCH transmissions, as illustrated in thethird row of the FIG. 9 , which shows uplink TCI states.

However, without a sounding reference signal (SRS) transmission, the BSmay not be able to determine (and indicate) precoding metrics andtargeted rank for the uplink TCI codebook for the PUSCH transmission.

According to aspects of the present disclosure, uplink TCI states withdownlink RS may be applied to codebook based PUSCH transmissions.

FIG. 11 illustrates example operations 1100 for wireless communicationsby a UE, in accordance with certain aspects of the present disclosure.The operations 1100 may be performed, for example, by a UE (e.g., UE 120a in the wireless communication network 100). The operations 1100 may beimplemented as software components that are executed and run on one ormore processors (e.g., controller/processor 280 of FIG. 2 ). Further,the transmission and reception of signals by the UE in operations 1100may be enabled, for example, by one or more antennas (e.g., antennas 252of FIG. 2 ). In certain aspects, the transmission and/or reception ofsignals by the UE may be implemented via a bus interface of one or moreprocessors (e.g., controller/processor 280) obtaining and/or outputtingsignals.

Operations 1100 begin, at 1102, by receiving, from a network entity,signaling of an uplink TCI state for a target codebook based uplinktransmission signal.

At 1104, the UE determines if the TCI state has a source downlink RS.

At 1106, the UE decides how to process the codebook based uplinktransmission based on the determination.

FIG. 12 illustrates example operations 1200 for wireless communicationsby a network entity, in accordance with certain aspects of the presentdisclosure. The operations 1200 may be performed, for example, by a BS(e.g., BS 110 a in the wireless communication network 100, which may bea gNB). The operations 1200 may be complementary to the operations 1200performed by the UE. The operations 1200 may be implemented as softwarecomponents that are executed and run on one or more processors (e.g.,controller/processor 240 of FIG. 2 ). Further, the transmission andreception of signals by the BS in operations 1200 may be enabled, forexample, by one or more antennas (e.g., antennas 234 of FIG. 2 ). Incertain aspects, the transmission and/or reception of signals by the BSmay be implemented via a bus interface of one or more processors (e.g.,controller/processor 240) obtaining and/or outputting signals.

Operations 1200 begin, at 1202, by sending, to a user equipment (UE),signaling of an uplink TCI state for a target codebook based uplinktransmission signal.

At 1204, the network entity determines how the UE processed the codebookbased uplink transmission, based on whether the TCI state has a sourcedownlink RS.

At 1206, the network entity processes the codebook based uplinktransmission in accordance with the determination.

In this manner, uplink TCI states with downlink source RS may be appliedto codebook based uplink transmissions, such as PUSCH.

In some cases, uplink TCI states with downlink source RS may not beapplied to codebook based PUSCH transmissions. Accordingly, for suchcodebook based PUSCH transmissions, the source RS may be an uplink RS(e.g., SRS) instead.

In some cases, a first downlink RS may be transmitted to the UE beforean uplink TCI state with a second downlink RS is transmitted. In thiscase, the UE may report measurements for transmission rank indication(TRI) and/or transmit precoding matrix indicator (TPMI) determination,based on the first downlink RS.

In such cases, the first downlink RS used for TRI/TPMI determination maybe the same as or different from the second downlink RS indicated in theuplink TCI state. The determined TRI/TPMI may be signalled in uplink TCIstates. For example, the determined TRI/TPMI are signalled with TCIstate when the two downlink RSs are different (and the UE may use thesignalled TRI/TPMI).

Otherwise, if the two downlink RSs are of the same type, the determinedTRI/TPMI may not need to be signalled (with the UL TCI state) becausethe UE may in effect learn (“memorize”) the TRI/TPMI determined based onthe first downlink RS (as it is the same type as the second downlinkRS). In some cases, the UE may determine the TRI/TPMI based on the firstdownlink RS.

If the uplink TCI state indicates the TRI/TPMI parameters to use, thenthe UE may use those signalled parameters. In an example, a single bitin the downlink control information (DCI) may indicate whether the UEmay use the same or different TRI/TPMI parameters.

In some cases, a SRS resource indictor (SRI) and TRI/TPMI may betransmitted with the uplink TCI state, as shown in FIG. 13 and FIG. 14 .

FIG. 13 illustrates a call flow of codebook based PUSCH transmission,similar to FIG. 10 . As illustrated, the UE transmits SRS to a BS beforean uplink TCI state with the downlink RS. The BS determines TRI/TPMIbased on the SRS. The BS may update the uplink TCI state to carry thedetermined TRI/TPMI, and transmits the uplink TCI state with thedownlink RS, the SRI, and the determined TRI/TPMI. The UE may thentransmit PUSCH based on the TPMI signalled with the UL TCI state.

As illustrated in FIG. 14 , in some cases, the UL TCI and theSRI/TRI/TPMI may be conveyed in different signals. In the illustratedexample, the uplink TCI and SRI are indicated in one signal (e.g., viaDCI), while the TRI/TPMI is conveyed in a second signal (e.g., viaMAC-CE).

FIG. 15 illustrates a communications device 1600 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 12 . Thecommunications device 1500 includes a processing system 1502 coupled toa transceiver 1508 (e.g., a transmitter and/or a receiver). Thetransceiver 1508 is configured to transmit and receive signals for thecommunications device 1500 via an antenna 1510, such as the varioussignals as described herein. The processing system 1502 may beconfigured to perform processing functions for the communications device1500, including processing signals received and/or to be transmitted bythe communications device 1500.

The processing system 1502 includes a processor 1504 coupled to acomputer-readable medium/memory 1512 via a bus 1506. In certain aspects,the computer-readable medium/memory 1512 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1504, cause the processor 1504 to perform the operationsillustrated in FIG. 12 , or other operations for performing the varioustechniques discussed herein for applying uplink TCI states with downlinkreference signals to codebook based PUSCH transmissions. In certainaspects, computer-readable medium/memory 1512 stores code 1514 forreceiving, from a network entity, signaling of an uplink TCI state for atarget codebook based uplink transmission signal; code 1516 fordetermining if the TCI state has a source downlink RS; and code 1518 fordeciding how to process the codebook based uplink transmission based onthe determination. In certain aspects, the processor 1504 has circuitryconfigured to implement the code stored in the computer-readablemedium/memory 1512. The processor 1504 includes circuitry 1524 forreceiving, from a network entity, signaling of an uplink TCI state for atarget codebook based uplink transmission signal; circuitry 1526 forsignaling of an uplink TCI state for a target codebook based uplinktransmission signal; code 1515 for determining if the TCI state has asource downlink RS; and circuitry 1528 for deciding how to process thecodebook based uplink transmission based on the determination.

For example, means for receiving (or means for obtaining) may include areceiver and/or antenna(s) 252 of the UE 120 a illustrated in FIG. 2and/or circuitry 1524 for receiving, from a network entity, signaling ofan uplink TCI state for a target codebook based uplink transmissionsignal of the communication device 1500 in FIG. 15 . Means forcommunicating may include a transmitter, a receiver or both. Means forgenerating, means for performing, means for determining, means fortaking action, means for determining, means for coordinating may includea processing system, which may include one or more processors, such asthe receive processor 258, the transmit processor 264, the TX MIMOprocessor 266, and/or the controller/processor 280 of the UE 120 aillustrated in FIG. 2 and/or the processing system 1502 of thecommunication device 1500 in FIG. 15 .

FIG. 16 illustrates a communications device 1600 that may includevarious components (e.g., corresponding to means-plus-functioncomponents) configured to perform operations for the techniquesdisclosed herein, such as the operations illustrated in FIG. 12 . Thecommunications device 1600 includes a processing system 1602 coupled toa transceiver 1608 (e.g., a transmitter and/or a receiver). Thetransceiver 1608 is configured to transmit and receive signals for thecommunications device 1600 via an antenna 1610, such as the varioussignals as described herein. The processing system 1602 may beconfigured to perform processing functions for the communications device1600, including processing signals received and/or to be transmitted bythe communications device 1600.

The processing system 1602 includes a processor 1604 coupled to acomputer-readable medium/memory 1612 via a bus 1606. In certain aspects,the computer-readable medium/memory 1612 is configured to storeinstructions (e.g., computer-executable code) that when executed by theprocessor 1604, cause the processor 1604 to perform the operationsillustrated in FIG. 12 , or other operations for performing the varioustechniques discussed herein for applying uplink TCI states with downlinkreference signals to codebook based PUSCH transmissions. In certainaspects, computer-readable medium/memory 1612 stores code 1614 forsending, to a UE, signaling of an uplink TCI state for a target codebookbased uplink transmission signal; code 1616 for determining how the UEprocessed the codebook based uplink transmission, based on whether theTCI state has a source downlink RS; and code 1618 for processing thecodebook based uplink transmission in accordance with the determination.In certain aspects, the processor 1604 has circuitry configured toimplement the code stored in the computer-readable medium/memory 1612.The processor 1604 includes circuitry 1624 for sending, to a UE,signaling of an uplink TCI state for a target codebook based uplinktransmission signal; circuitry 1626 for determining how the UE processedthe codebook based uplink transmission, based on whether the TCI statehas a source downlink RS; and circuitry 1628 for processing the codebookbased uplink transmission in accordance with the determination.

For example, means for transmitting (or means for outputting fortransmission) may include the transmitter unit 254 and/or antenna(s) 252of the UE 120 a illustrated in FIG. 2 and/or circuitry 1624 for sending,to a UE, signaling of an uplink TCI state for a target codebook baseduplink transmission signal of the communication device 1600 in FIG. 16 .Means for communicating may include a transmitter, a receiver or both.Means for generating, means for performing, means for determining, meansfor taking action, means for determining, means for coordinating mayinclude a processing system, which may include one or more processors,such as the receive processor 258, the transmit processor 264, the TXMIMO processor 266, and/or the controller/processor 280 of the UE 120 aillustrated in FIG. 2 and/or the processing system 1602 of thecommunication device 1600 in FIG. 16 .

Example Aspects

In a first aspect, a method of wireless communications by a userequipment (UE), includes: receiving, from a network entity, signaling ofan uplink transmission configuration indicator (TCI) state for a targetcodebook based uplink transmission signal; determining if the TCI statehas a source downlink reference signal (RS); and deciding how to processthe codebook based uplink transmission based on the determination.

In a second aspect, in combination with the first aspect, the codebookbased uplink transmission comprises a physical uplink shared channel(PUSCH).

In a third aspect, in combination with any of the first through secondaspects, if the determination is the uplink TCI state has a sourcedownlink RS, the decision is to not apply the TCI state to the codebookbased uplink transmission.

In a fourth aspect, in combination with any of the first through thirdaspects, uplink transmission parameters have been determined based on afirst downlink RS prior to receiving the TCI state; the TCI state has asecond downlink RS as a source downlink RS; and deciding how to processthe codebook based uplink transmission depends, at least in part, if thefirst downlink RS and second downlink RS are of a same type.

In a fifth aspect, in combination with the fourth aspect, the type offirst downlink RS and second downlink RS comprises one of: a first QCLtype that indicates QCL assumptions regarding Doppler shift, Dopplerspread, average delay, and delay spread; a second QCL type thatindicates QCL assumptions regarding Doppler shift and Doppler spread; athird QCL type that indicates Doppler shift and average delay; and afourth QCL type that indicates QCL assumptions regarding spatialrelations.

In a sixth aspect, in combination with any of the fourth and fifthaspects, n the decision is to use the previously determined transmissionparameters if the first and second downlink RS are the same type.

In a seventh aspect, in combination with any of the fourth through sixthaspects, the decision is to use transmission parameters signaled withthe uplink TCI state if the first and second downlink RS are ofdifferent types.

In an eighth aspect, in combination with the seventh aspect, the uplinktransmission parameters are indicated in the UL TCI in addition to thesource downlink RS.

In a ninth aspect, in combination with any of the fourth through eighthaspects, the method further includes determining the uplink transmissionparameters based on a first downlink RS prior to receiving the TCIstate.

In a tenth aspect, in combination with any of the fourth through ninthaspects, the first and the second downlink RS are the same downlink RS.

In a eleventh aspect, in combination with any of the first through tenthaspects, the method further includes transmitting sounding referencesignals (SRS) to the network entity prior to receiving the uplink TCIstate; and receiving uplink transmission parameters from the networkentity based on the SRS; wherein the decision is to apply the uplinktransmission parameters and UL TCI state for the codebook based uplinktransmission.

In a twelfth aspect, in combination with the eleventh aspect, at leastsome of the uplink transmission parameters are signaled separately fromthe UL TCI state.

In a thirteenth aspect, in combination with any of the eleventh andtwelfth aspects, the uplink transmission parameters are indicated in theUL TCI in addition to the source downlink RS.

In a fourteenth aspect, in combination with any of the fourth throughthirteenth aspects, the uplink transmission parameters comprise at leastone of a transmission rank indication (TRI), transmit precoding matrixindicator (TPMI), or SRS resource indicator (SRI).

In a fifteenth aspect, a method of wireless communications by a networkentity, includes: sending, to a user equipment (UE), signaling of anuplink transmission configuration indicator (TCI) state for a targetcodebook based uplink transmission signal; determining how the UEprocessed the codebook based uplink transmission, based on whether theTCI state has a source downlink reference signal (RS); and processingthe codebook based uplink transmission in accordance with thedetermination.

In a sixteenth aspect, in combination with the fifteenth aspect, thecodebook based uplink transmission comprises a physical uplink sharedchannel (PUSCH).

In a seventeenth aspect, in combination with the fifteenth and sixteenthaspects, if the uplink TCI state has a source downlink RS, thedetermination is that the UE did not apply the TCI state to the codebookbased uplink transmission.

In an eighteenth aspect, in combination with any of the fifteenththrough seventeenth aspects, uplink transmission parameters have beendetermined based on a first downlink RS prior to sending the TCI state;the TCI state has a second downlink RS as a source downlink RS; anddetermining how the UE processed the codebook based uplink transmissiondepends, at least in part, if the first downlink RS and second downlinkRS are of a same type.

In a nineteenth aspect, in combination with the eighteenth aspect, thetype of first downlink RS and second downlink RS comprises one of: afirst QCL type that indicates QCL assumptions regarding Doppler shift,Doppler spread, average delay, and delay spread; a second QCL type thatindicates QCL assumptions regarding Doppler shift and Doppler spread; athird QCL type that indicates Doppler shift and average delay; and afourth QCL type that indicates QCL assumptions regarding spatialrelations.

In a twentieth aspect, in combination with any of the eighteenth throughnineteenth aspects, the determination is the UE used the previouslydetermined transmission parameters if the first and second downlink RSare the same type.

In a twenty-first aspect, in combination with any of the eighteenththrough twentieth aspects, the determination is the UE used transmissionparameters signaled with the uplink TCI state if the first and seconddownlink RS are of different types.

In a twenty-second aspect, in combination with the twenty-first aspect,the network entity indicates the uplink transmission parameters in theuplink TCI in addition to the source downlink RS.

In a twenty-third aspect, in combination with any of the eighteenththrough twenty-second aspects, the UE determines the uplink transmissionparameters based on a first downlink RS prior to receiving the TCIstate.

In a twenty-fourth aspect, in combination with any of the eighteenththrough twenty-third aspects, the first and the second downlink RS arethe same downlink RS.

In a twenty-fifth aspect, in combination with any of the fifteenththrough twenty-fourth aspects, the method further includes: receivingsounding reference signals (SRS) from the UE prior to sending the uplinkTCI state; and transmitting uplink transmission parameters to the UEbased on the SRS; wherein the determination is the UE applied the uplinktransmission parameters and UL TCI state for the codebook based uplinktransmission.

In a twenty-sixth aspect, in combination with the twenty-fifth aspect,at least some of the uplink transmission parameters are signaledseparately from the UL TCI state.

In a twenty-seventh aspect, in combination with any of the twenty-fifthand twenty-sixth aspects, the uplink transmission parameters areindicated in the UL TCI in addition to the source downlink RS.

In a twenty-eighth aspect, in combination with any of the eighteenththrough twenty-seventh aspects, the uplink transmission parameterscomprise at least one of a transmission rank indication (TRI), transmitprecoding matrix indicator (TPMI), or SRS resource indicator (SRI).

The techniques described herein may be used for various wirelesscommunication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA,SC-FDMA and other networks. The terms “network” and “system” are oftenused interchangeably. A CDMA network may implement a radio technologysuch as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRAincludes Wideband CDMA (WCDMA) and other variants of CDMA. cdma2000covers IS-2000, IS-95 and IS-856 standards. A TDMA network may implementa radio technology such as Global System for Mobile Communications(GSM). An OFDMA network may implement a radio technology such as NR(e.g. 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRAand E-UTRA are part of Universal Mobile Telecommunication System (UMTS).LTE and LTE-A are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS,LTE, LTE-A and GSM are described in documents from an organization named“3rd Generation Partnership Project” (3GPP). cdma2000 and UMB aredescribed in documents from an organization named “3rd GenerationPartnership Project 2” (3GPP2). NR is an emerging wirelesscommunications technology under development.

In 3GPP, the term “cell” can refer to a coverage area of a Node B (NB)and/or a NB subsystem serving this coverage area, depending on thecontext in which the term is used. In NR systems, the term “cell” andBS, next generation NodeB (gNB or gNodeB), access point (AP),distributed unit (DU), carrier or transmission reception point (TRP) maybe used interchangeably.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or other types of cells. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having an association with the femto cell(e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in thehome, etc.). A BS for a macro cell may be referred to as a macro BS. ABS for a pico cell may be referred to as a pico BS. A BS for a femtocell may be referred to as a femto BS or a home BS.

A UE may also be referred to as a mobile station, a terminal, an accessterminal, a subscriber unit, a station, a Customer Premises Equipment(CPE), a cellular phone, a smart phone, a personal digital assistant(PDA), a wireless modem, a wireless communication device, a handhelddevice, a laptop computer, a cordless phone, a wireless local loop (WLL)station, a tablet computer, a camera, a gaming device, a netbook, asmartbook, an ultrabook, an appliance, a medical device or medicalequipment, a biometric sensor/device, a wearable device such as a smartwatch, smart clothing, smart glasses, a smart wrist band, smart jewelry(e.g., a smart ring, a smart bracelet, etc.), an entertainment device(e.g., a music device, a video device, a satellite radio, etc.), avehicular component or sensor, a smart meter/sensor, industrialmanufacturing equipment, a global positioning system device, gamingdevice, reality augmentation device (augmented reality (AR), extendedreality (XR), or virtual reality (VR)), or any other suitable devicethat is configured to communicate via a wireless or wired medium.

Some UEs may be considered machine-type communication (MTC) devices orevolved MTC (eMTC) devices. MTC and eMTC UEs include, for example,robots, drones, remote devices, sensors, meters, monitors, locationtags, etc., that may communicate with a BS, another device (e.g., remotedevice), or some other entity. A wireless node may provide, for example,connectivity for or to a network (e.g., a wide area network such asInternet or a cellular network) via a wired or wireless communicationlink. Some UEs may be considered Internet-of-Things (IoT) devices, whichmay be narrowband IoT (NB-IoT) devices.

In some scenarios, air interface access may be scheduled. For example, ascheduling entity (e.g., a base station (BS), Node B, eNB, gNB, or thelike) can allocate resources for communication among some or all devicesand equipment within its service area or cell. The scheduling entity maybe responsible for scheduling, assigning, reconfiguring, and releasingresources for one or more subordinate entities. That is, for scheduledcommunication, subordinate entities can utilize resources allocated byone or more scheduling entities. Base stations are not the only entitiesthat may function as a scheduling entity. In some examples, a UE mayfunction as a scheduling entity and may schedule resources for one ormore subordinate entities (e.g., one or more other UEs), and the otherUEs may utilize the resources scheduled by the UE for wirelesscommunication. In some examples, a UE may function as a schedulingentity in a peer-to-peer (P2P) network, and/or in a mesh network. In amesh network example, UEs may communicate directly with one another inaddition to communicating with a scheduling entity.

The methods disclosed herein comprise one or more steps or actions forachieving the methods. The method steps and/or actions may beinterchanged with one another without departing from the scope of theclaims. In other words, unless a specific order of steps or actions isspecified, the order and/or use of specific steps and/or actions may bemodified without departing from the scope of the claims.

As used herein, a phrase referring to “at least one of” a list of itemsrefers to any combination of those items, including single members. Asan example, “at least one of: a, b, or c” is intended to cover a, b, c,a-b, a-c, b-c, and a-b-c, as well as any combination with multiples ofthe same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b,b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c).

As used herein, the term “determining” encompasses a wide variety ofactions. For example, “determining” may include calculating, computing,processing, deriving, investigating, looking up (e.g., looking up in atable, a database or another data structure), ascertaining and the like.Also, “determining” may include receiving (e.g., receiving information),accessing (e.g., accessing data in a memory) and the like. Also,“determining” may include resolving, selecting, choosing, establishingand the like.

The previous description is provided to enable any person skilled in theart to practice the various aspects described herein. Variousmodifications to these aspects will be readily apparent to those skilledin the art, and the generic principles defined herein may be applied toother aspects. Thus, the claims are not intended to be limited to theaspects shown herein, but is to be accorded the full scope consistentwith the language of the claims, wherein reference to an element in thesingular is not intended to mean “one and only one” unless specificallyso stated, but rather “one or more.” Unless specifically statedotherwise, the term “some” refers to one or more. All structural andfunctional equivalents to the elements of the various aspects describedthroughout this disclosure that are known or later come to be known tothose of ordinary skill in the art are expressly incorporated herein byreference and are intended to be encompassed by the claims. Moreover,nothing disclosed herein is intended to be dedicated to the publicregardless of whether such disclosure is explicitly recited in theclaims. No claim element is to be construed under the provisions of 35U.S.C. § 112(f) unless the element is expressly recited using the phrase“means for” or, in the case of a method claim, the element is recitedusing the phrase “step for.”

The various operations of methods described above may be performed byany suitable means capable of performing the corresponding functions.The means may include various hardware and/or software component(s)and/or module(s), including, but not limited to a circuit, anapplication specific integrated circuit (ASIC), or processor. Generally,where there are operations illustrated in figures, those operations mayhave corresponding counterpart means-plus-function components withsimilar numbering.

The various illustrative logical blocks, modules and circuits describedin connection with the present disclosure may be implemented orperformed with a general purpose processor, a digital signal processor(DSP), an application specific integrated circuit (ASIC), a fieldprogrammable gate array (FPGA) or other programmable logic device (PLD),discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any commercially available processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in hardware, an example hardware configuration maycomprise a processing system in a wireless node. The processing systemmay be implemented with a bus architecture. The bus may include anynumber of interconnecting buses and bridges depending on the specificapplication of the processing system and the overall design constraints.The bus may link together various circuits including a processor,machine-readable media, and a bus interface. The bus interface may beused to connect a network adapter, among other things, to the processingsystem via the bus. The network adapter may be used to implement thesignal processing functions of the PHY layer. In the case of a userterminal 120 (see FIG. 1 ), a user interface (e.g., keypad, display,mouse, joystick, etc.) may also be connected to the bus. The bus mayalso link various other circuits such as timing sources, peripherals,voltage regulators, power management circuits, and the like, which arewell known in the art, and therefore, will not be described any further.The processor may be implemented with one or more general-purpose and/orspecial-purpose processors. Examples include microprocessors,microcontrollers, DSP processors, and other circuitry that can executesoftware. Those skilled in the art will recognize how best to implementthe described functionality for the processing system depending on theparticular application and the overall design constraints imposed on theoverall system.

If implemented in software, the functions may be stored or transmittedover as one or more instructions or code on a computer readable medium.Software shall be construed broadly to mean instructions, data, or anycombination thereof, whether referred to as software, firmware,middleware, microcode, hardware description language, or otherwise.Computer-readable media include both computer storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. The processor may beresponsible for managing the bus and general processing, including theexecution of software modules stored on the machine-readable storagemedia. A computer-readable storage medium may be coupled to a processorsuch that the processor can read information from, and write informationto, the storage medium. In the alternative, the storage medium may beintegral to the processor. By way of example, the machine-readable mediamay include a transmission line, a carrier wave modulated by data,and/or a computer readable storage medium with instructions storedthereon separate from the wireless node, all of which may be accessed bythe processor through the bus interface. Alternatively, or in addition,the machine-readable media, or any portion thereof, may be integratedinto the processor, such as the case may be with cache and/or generalregister files. Examples of machine-readable storage media may include,by way of example, RAM (Random Access Memory), flash memory, ROM (ReadOnly Memory), PROM (Programmable Read-Only Memory), EPROM (ErasableProgrammable Read-Only Memory), EEPROM (Electrically ErasableProgrammable Read-Only Memory), registers, magnetic disks, opticaldisks, hard drives, or any other suitable storage medium, or anycombination thereof. The machine-readable media may be embodied in acomputer-program product.

A software module may comprise a single instruction, or manyinstructions, and may be distributed over several different codesegments, among different programs, and across multiple storage media.The computer-readable media may comprise a number of software modules.The software modules include instructions that, when executed by anapparatus such as a processor, cause the processing system to performvarious functions. The software modules may include a transmissionmodule and a receiving module. Each software module may reside in asingle storage device or be distributed across multiple storage devices.By way of example, a software module may be loaded into RAM from a harddrive when a triggering event occurs. During execution of the softwaremodule, the processor may load some of the instructions into cache toincrease access speed. One or more cache lines may then be loaded into ageneral register file for execution by the processor. When referring tothe functionality of a software module below, it will be understood thatsuch functionality is implemented by the processor when executinginstructions from that software module.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, server, or otherremote source using a coaxial cable, fiber optic cable, twisted pair,digital subscriber line (DSL), or wireless technologies such as infrared(IR), radio, and microwave, then the coaxial cable, fiber optic cable,twisted pair, DSL, or wireless technologies such as infrared, radio, andmicrowave are included in the definition of medium. Disk and disc, asused herein, include compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk, and Blu-ray® disc where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Thus, in some aspects computer-readable media maycomprise non-transitory computer-readable media (e.g., tangible media).In addition, for other aspects computer-readable media may comprisetransitory computer-readable media (e.g., a signal). Combinations of theabove should also be included within the scope of computer-readablemedia.

Thus, certain aspects may comprise a computer program product forperforming the operations presented herein. For example, such a computerprogram product may comprise a computer-readable medium havinginstructions stored (and/or encoded) thereon, the instructions beingexecutable by one or more processors to perform the operations describedherein. For example, instructions for performing the operationsdescribed herein and illustrated in FIGS. 11 and 12 .

Further, it should be appreciated that modules and/or other appropriatemeans for performing the methods and techniques described herein can bedownloaded and/or otherwise obtained by a user terminal and/or basestation as applicable. For example, such a device can be coupled to aserver to facilitate the transfer of means for performing the methodsdescribed herein. Alternatively, various methods described herein can beprovided via storage means (e.g., RAM, ROM, a physical storage mediumsuch as a compact disc (CD) or floppy disk, etc.), such that a userterminal and/or base station can obtain the various methods uponcoupling or providing the storage means to the device. Moreover, anyother suitable technique for providing the methods and techniquesdescribed herein to a device can be utilized.

It is to be understood that the claims are not limited to the preciseconfiguration and components illustrated above. Various modifications,changes and variations may be made in the arrangement, operation anddetails of the methods and apparatus described above without departingfrom the scope of the claims.

What is claimed is:
 1. A method of wireless communications by a userequipment (UE), comprising: receiving, from a network entity, signalingof an uplink transmission configuration indicator (TCI) state for atarget codebook based uplink transmission signal; determining if the TCIstate has a source downlink reference signal (RS); and deciding how toprocess the codebook based uplink transmission based on thedetermination.
 2. The method of claim 1, wherein the codebook baseduplink transmission comprises a physical uplink shared channel (PUSCH).3. The method of claim 1, wherein, if the determination is the uplinkTCI state has a source downlink RS, the decision is to not apply the TCIstate to the codebook based uplink transmission.
 4. The method of claim1, wherein: uplink transmission parameters have been determined based ona first downlink RS prior to receiving the TCI state; the TCI state hasa second downlink RS as a source downlink RS; and deciding how toprocess the codebook based uplink transmission depends, at least inpart, if the first downlink RS and second downlink RS are of a sametype.
 5. The method of claim 4, wherein the type of first downlink RSand second downlink RS comprises one of: a first QCL type that indicatesQCL assumptions regarding Doppler shift, Doppler spread, average delay,and delay spread; a second QCL type that indicates QCL assumptionsregarding Doppler shift and Doppler spread; a third QCL type thatindicates Doppler shift and average delay; and a fourth QCL type thatindicates QCL assumptions regarding spatial relations.
 6. The method ofclaim 4, wherein the decision is to use the previously determinedtransmission parameters if the first and second downlink RS are the sametype.
 7. The method of claim 4, wherein the decision is to usetransmission parameters signaled with the uplink TCI state if the firstand second downlink RS are of different types.
 8. The method of claim 7,wherein the uplink transmission parameters are indicated in the UL TCIin addition to the source downlink RS.
 9. The method of claim 4, furthercomprising: determining the uplink transmission parameters based on afirst downlink RS prior to receiving the TCI state.
 10. The method ofclaim 4, wherein the first and the second downlink RS are the samedownlink RS.
 11. The method of claim 1, further comprising: transmittingsounding reference signals (SRS) to the network entity prior toreceiving the uplink TCI state; and receiving uplink transmissionparameters from the network entity based on the SRS; wherein thedecision is to apply the uplink transmission parameters and UL TCI statefor the codebook based uplink transmission.
 12. The method of claim 11,wherein at least some of the uplink transmission parameters are signaledseparately from the UL TCI state.
 13. The method of claim 11, whereinthe uplink transmission parameters are indicated in the UL TCI inaddition to the source downlink RS.
 14. The method of claim 4, whereinthe uplink transmission parameters comprise at least one of atransmission rank indication (TRI), transmit precoding matrix indicator(TPMI), or SRS resource indicator (SRI).
 15. A method of wirelesscommunications by a network entity, comprising: sending, to a userequipment (UE), signaling of an uplink transmission configurationindicator (TCI) state for a target codebook based uplink transmissionsignal; determining how the UE processed the codebook based uplinktransmission, based on whether the TCI state has a source downlinkreference signal (RS); and processing the codebook based uplinktransmission in accordance with the determination.
 16. The method ofclaim 15, wherein the codebook based uplink transmission comprises aphysical uplink shared channel (PUSCH).
 17. The method of claim 15,wherein, if the uplink TCI state has a source downlink RS, thedetermination is that the UE did not apply the TCI state to the codebookbased uplink transmission.
 18. The method of claim 15, wherein: uplinktransmission parameters have been determined based on a first downlinkRS prior to sending the TCI state; the TCI state has a second downlinkRS as a source downlink RS; and determining how the UE processed thecodebook based uplink transmission depends, at least in part, if thefirst downlink RS and second downlink RS are of a same type.
 19. Themethod of claim 18, wherein the type of first downlink RS and seconddownlink RS comprises one of: a first QCL type that indicates QCLassumptions regarding Doppler shift, Doppler spread, average delay, anddelay spread; a second QCL type that indicates QCL assumptions regardingDoppler shift and Doppler spread; a third QCL type that indicatesDoppler shift and average delay; and a fourth QCL type that indicatesQCL assumptions regarding spatial relations.
 20. The method of claim 18,wherein the determination is the UE used the previously determinedtransmission parameters if the first and second downlink RS are the sametype.
 21. The method of claim 18, wherein the determination is the UEused transmission parameters signaled with the uplink TCI state if thefirst and second downlink RS are of different types.
 22. The method ofclaim 21, wherein the network entity indicates the uplink transmissionparameters in the uplink TCI in addition to the source downlink RS. 23.The method of claim 18, wherein the UE determines the uplinktransmission parameters based on a first downlink RS prior to receivingthe TCI state.
 24. The method of claim 18, wherein the first and thesecond downlink RS are the same downlink RS.
 25. The method of claim 15,further comprising: receiving sounding reference signals (SRS) from theUE prior to sending the uplink TCI state; and transmitting uplinktransmission parameters to the UE based on the SRS; wherein thedetermination is the UE applied the uplink transmission parameters andUL TCI state for the codebook based uplink transmission.
 26. The methodof claim 25, wherein at least some of the uplink transmission parametersare signaled separately from the UL TCI state.
 27. The method of claim25, wherein the uplink transmission parameters are indicated in the ULTCI in addition to the source downlink RS.
 28. The method of claim 18,wherein the uplink transmission parameters comprise at least one of atransmission rank indication (TRI), transmit precoding matrix indicator(TPMI), or SRS resource indicator (SRI).
 29. An apparatus of wirelesscommunications, comprising: at least one processor; and memory coupledto the at least one processor, the memory comprising code executable bythe at least one processor to cause the apparatus to: receive, from anetwork entity, signaling of an uplink transmission configurationindicator (TCI) state for a target codebook based uplink transmissionsignal; determine if the TCI state has a source downlink referencesignal (RS); and decide how to process the codebook based uplinktransmission based on the determination.
 30. An apparatus of wirelesscommunications, comprising: at least one processor; and memory coupledto the at least one processor, the memory comprising code executable bythe at least one processor to cause the apparatus to: send, to a userequipment (UE), signaling of an uplink transmission configurationindicator (TCI) state for a target codebook based uplink transmissionsignal; determine how the UE processed the codebook based uplinktransmission, based on whether the TCI state has a source downlinkreference signal (RS); and process the codebook based uplinktransmission in accordance with the determination.